Skip to content

MQTTReader: make client_name optional and ensure client_id is unique#577

Merged
davidpablocohn merged 1 commit into
OceanDataTools:masterfrom
veggiemike:for-upstream/mqttreader-unique-client-id
Jun 23, 2026
Merged

MQTTReader: make client_name optional and ensure client_id is unique#577
davidpablocohn merged 1 commit into
OceanDataTools:masterfrom
veggiemike:for-upstream/mqttreader-unique-client-id

Conversation

@veggiemike

Copy link
Copy Markdown
Contributor

This commit makes the client_name constructor param optional, allowing the underlying Paho MQTT library to generate a random ID as needed. If client_name is provided, it is appended with 6 random characters to help ensure uniqueness.

W/out this patch, if you accidentally supply the same client_name for multiple readers (say, via a template), each new connection causes the broker to disconnect all previous instances, and only the last instance receives messages.

This commit makes the `client_name` constructor param optional, allowing
the underlying Paho MQTT library to generate a random ID as needed.  If
`client_name` is provided, it is appended with 6 random characters to help
ensure uniqueness.
@davidpablocohn davidpablocohn merged commit 366e6bb into OceanDataTools:master Jun 23, 2026
1 check passed
@davidpablocohn

Copy link
Copy Markdown
Collaborator

Ah - just realized we merged this into master. In general I like to stage by merging into dev first. I'll go ahead and cherry pick the change, then merge it into dev as well.

davidpablocohn added a commit that referenced this pull request Jun 23, 2026
…577) (#579)

This commit makes the `client_name` constructor param optional, allowing
the underlying Paho MQTT library to generate a random ID as needed.  If
`client_name` is provided, it is appended with 6 random characters to help
ensure uniqueness.

Co-authored-by: Michael D Labriola <mdlabriola@oceanexplorationtrust.org>
@veggiemike

Copy link
Copy Markdown
Contributor Author

Ah - just realized we merged this into master. In general I like to stage by merging into dev first. I'll go ahead and cherry pick the change, then merge it into dev as well.

Oops, that's my bad. I didn't even think about it when I wrote the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants